Skip to content

remoteproc_virtio: add shm_io for remoteproc virtio#542

Draft
CV-Bowen wants to merge 1 commit into
OpenAMP:mainfrom
CV-Bowen:rproc-virtio-shmio
Draft

remoteproc_virtio: add shm_io for remoteproc virtio#542
CV-Bowen wants to merge 1 commit into
OpenAMP:mainfrom
CV-Bowen:rproc-virtio-shmio

Conversation

@CV-Bowen

@CV-Bowen CV-Bowen commented Dec 4, 2023

Copy link
Copy Markdown
Contributor

Now the rpmsg device need pass a share memory io region to rpmsg_init_vdev().
I think every virtio device need a share memory io to access the share memory and this region should be provided by the transport layer. Like the MMIO transport layer did in OpenAMP.

So I add shm_io in the remoteproc virtio device and also provide an API to set it.

Now the rpmsg device need pass a share memory io region to
rpmsg_init_vdev().
I think every virtio device need a share memory io to access the share
memory and this region should be provided by the transport layer.
Like the MMIO transport layer did in OpenAMP.

So I add shm_io in the remoteproc virtio device and also provide a API
to set it.

Signed-off-by: Bowen Wang <wangbowen6@xiaomi.com>
@arnopo arnopo requested review from arnopo, edmooring and tnmysh December 8, 2023 09:25
@tnmysh

tnmysh commented Dec 18, 2023

Copy link
Copy Markdown
Collaborator

Any usage of this API anywhere ? Either in demos or OpenAMP ?
If not, may be not right time to have this change.
Also we don't alwasy assume shm_io will be always used. dmabuf based memory allocation is also possible. I think such use case was posted by TI in another PR.

@arnopo, @edmooring any thoughts?

@arnopo

arnopo commented Dec 19, 2023

Copy link
Copy Markdown
Collaborator

Quite agree with @tnmysh. This PR introduces an unused field. If possible I would prefer it to be integrated in a PR that provides the full picture of the need.

@tnmysh : I remember we discussed the possibility of using dmabuf-based memory allocation in a meeting, but I don't see any associated PR or issue. Could you please provide a reference if you have it?

@edmooring edmooring left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are there any consumers for this new API? I can't find any in either open-amp or openamp-system-reference.

@CV-Bowen

CV-Bowen commented Jan 5, 2024

Copy link
Copy Markdown
Contributor Author

@arnopo @tnmysh @edmooring Thanks, I use this API in NuttX (but code not up streamed). We want make the remoteproc transport layer supports more virtio devices.
I will continue this PR when I up streamed the NuttX part code.

@CV-Bowen CV-Bowen marked this pull request as draft January 5, 2024 08:11
@github-actions

Copy link
Copy Markdown

This pull request has been marked as a stale pull request because it has been open (more than) 45 days with no activity.

@github-actions github-actions Bot added the Stale label Feb 20, 2024
@CV-Bowen

CV-Bowen commented Apr 9, 2024

Copy link
Copy Markdown
Contributor Author

@tnmysh : I remember we discussed the possibility of using dmabuf-based memory allocation in a meeting, but I don't see any associated PR or issue. Could you please provide a reference if you have it?

@tnmysh I want to continue this PR and I'm interested in the dma method. That will be very thankfully if you can proviud a reference if you have it.

@tnmysh

tnmysh commented Apr 9, 2024

Copy link
Copy Markdown
Collaborator

@arnopo , @CV-Bowen here is PR that mentions using dma-buf:

OpenAMP/libmetal#82

I remember TI folks were working to update that PR. Not sure about latest status.

@github-actions github-actions Bot removed the Stale label Apr 10, 2024
@github-actions

Copy link
Copy Markdown

This pull request has been marked as a stale pull request because it has been open (more than) 45 days with no activity.

@github-actions github-actions Bot added the Stale label May 25, 2024
@xiaoxiang781216

Copy link
Copy Markdown
Collaborator

don't need anymore? @CV-Bowen

@github-actions github-actions Bot removed the Stale label Oct 9, 2024
@github-actions

Copy link
Copy Markdown

This pull request has been marked as a stale pull request because it has been open (more than) 45 days with no activity.

@github-actions github-actions Bot added the Stale label Dec 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants